Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

reference: TREE 444
name
tree-preservation-order: undefined
05/09
uprn
address-text: South of Great Horkesley Manor,
point: POINT (0.883006 51.927196)
geometry: MULTIPOLYGON (((0.883214 51.927191,0.883212 51.927215,0.883203 51.927238,0.883193 51.927253,0.883180 51.927267,0.883164 51.927279,0.883146 51.927291,0.883126 51.927301,0.883093 51.927313,0.883056 51.927321,0.883018 51.927324,0.882966 51.927322,0.882941 51.927318,0.882917 51.927312,0.882884 51.927300,0.882864 51.927290,0.882846 51.927278,0.882831 51.927265,0.882813 51.927244,0.882802 51.927221,0.882799 51.927205,0.882800 51.927181,0.882805 51.927165,0.882812 51.927150,0.882829 51.927129,0.882844 51.927116,0.882871 51.927098,0.882881 51.927093,0.882914 51.927081,0.882950 51.927072,0.882988 51.927068,0.883040 51.927069,0.883077 51.927075,0.883123 51.927090,0.883144 51.927100,0.883170 51.927117,0.883191 51.927137,0.883209 51.927167,0.883214 51.927191)))
notes
felled-date
entry-date: 2026-08-01
start-date
end-date

Your data is missing a tree-preservation-order.

The Tree guidance explains how to fix the issue:

The reference for the tree preservation order that affects this tree.

Example: TPO1